0.0
NA
CVE-2026-3941
Google Chrome DevTools Policy Enforcement Bypass Vulnerability
Description

Insufficient policy enforcement in DevTools in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Low)

INFO

Published Date :

March 11, 2026, 10:16 p.m.

Last Modified :

March 11, 2026, 10:16 p.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-3941 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Update Google Chrome to version 146.0.7680.71 or later to fix navigation bypass vulnerabilities.
  • Update Google Chrome to the latest version.
  • Ensure all instances are updated to 146.0.7680.71 or newer.
Public PoC/Exploit Available at Github

CVE-2026-3941 has a 1 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-3941.

URL Resource
https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_10.html
https://issues.chromium.org/issues/474670215
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-3941 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-3941 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Community reconstruction of the legacy JSON NVD Data Feeds. This project uses and redistributes data from the NVD API but is neither endorsed nor certified by the NVD.

Shell

Updated: 2 hours, 12 minutes ago
211 stars 26 fork 26 watcher
Born at : May 17, 2023, 8 a.m. This repo has been linked 53 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-3941 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-3941 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Mar. 11, 2026

    Action Type Old Value New Value
    Added Description Insufficient policy enforcement in DevTools in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Low)
    Added Reference https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_10.html
    Added Reference https://issues.chromium.org/issues/474670215
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.